feat(discovery): manual network assets W03 — website/URL targets, partner inventory, docs, e2e (#5213) - #5260

#5213's manual network assets W02 (#5258) and W03 (#5260) landed while this
wave was open; both extend the same Devices surfaces. Resolution keeps both
features in full:

- DevicesPage: ONE Add control. main's inline split menu is folded into this
  wave's shared AddAssetMenu component, now three items (Install agent…,
  Add asset manually…, Add network asset…) in both the header and empty-state
  instances. Testids follow main's names (devices-page-add-menu*), so #5260's
  e2e spec is unchanged; this wave's Page Object was renamed to match. Side
  benefit: main's two instances shared one addMenuOpen flag (they opened
  together); AddAssetMenu holds per-instance state.
- Locale catalogs (8): structural 3-way JSON union, plus devicesPage.addAsset /
  installAgent / addManualAssetAction folded into devicesPage.addMenu.* so the
  two features share one namespace.
- DeviceList / columnVisibility: serial + assetTag + location (this wave) AND
  source (#5213) all kept.
- bulkActionGating: took main's dedicated
  deviceActions.unavailable.unknown string over this wave's notOnline reuse —
  a manual asset was never online, so "not online" is the less honest label.
- DeviceList.statusSortRank: kept this wave's ordering (decommissioned 6,
  unknown 7) — "no probe has ever run" is a different axis, not a state worse
  than offline.
- no-silent-mutations: both handlers registered, count 123 -> 125.
- translationCoverage: baselines recomputed as base + both deltas.

Verified: apps/web 828 files / 9336 tests pass; apps/web and apps/api tsc clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016tcUieLXQuupVjBUSZUn5j

…ec.ts's final assertion has a cell to read (#5265)

The spec's last step asserts the created row's device-<id>-source cell reads
"manual", but 'source' is an opt-in column (columnVisibility.ts:
DEFAULT_VISIBLE_COLUMNS deliberately excludes it — agent rows have no source,
so default-on would show a column of dashes for the common agent-only fleet).
That gap predates this fix branch: the opt-in decision shipped in W02 (#5258),
two commits before the spec itself was added in W03 (#5260) — so the
assertion was inconsistent with the shipped default from the start.

The Columns menu that toggles it carries no data-testid (out of that wave's
file-ownership scope), so seed the persisted localStorage preference directly
via addInitScript before the first navigation instead of driving that menu
with a non-testid selector. A single-entry columns list still gets every
other column its own catalog default via columnVisibility.ts's merge-on-read,
so this only adds 'source' visibility — no other column is affected.

Verified end-to-end against a worktree-stack: the spec now passes in full,
including the previously-blocked final assertion, confirming the DevicesPage
fix (previous commit) holds under a real browser refresh.

Refs #5265

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RTMowR8XgvbgZakWhtbiDv

… refresh (LanternOps#5265) (LanternOps#5271)

## Root cause

`AddNetworkAssetModal.onCreated` calls `DevicesPage.refreshDevices()`,
which flips `loading` back to `true`. Every DevicesPage render branch
(org-context-failed, loading, access-denied, error, main) was a
**separate `return`**, so the loading skeleton unmounted
`<AddNetworkAssetModal>` entirely instead of swapping only the content
underneath it — resetting the modal's internal `createdAsset` state to
`null` the instant the post-create HTTP-check hand-off panel
(`data-testid="asset-post-create"`) was supposed to appear.

## Fix

Hoisted `<AddNetworkAssetModal>` into a `Fragment` that wraps **every**
branch, always as the first child at the same tree position, so React
preserves the component instance across the `loading` transition — only
the second child (skeleton / error state / real content) swaps out
underneath it. This is the "move the modal above the early return" shape
from the issue's proposed fix, chosen over restructuring the loading
skeleton into the page body (would have required guarding a much larger
swath of JSX across four branches) and over lifting `createdAsset` into
page state (would have duplicated state the modal already owns correctly
— the bug is only that DevicesPage discards the component, not that the
state model is wrong).

Also fixed `e2e-tests/tests/manual-network-asset.spec.ts`: its final
assertion checks a `device-<id>-source` cell, but `source` is an opt-in
column (`columnVisibility.ts`) that predates this fix branch — the
opt-in decision shipped in W02 (LanternOps#5258), two commits before the spec was
added in W03 (LanternOps#5260), so the assertion was inconsistent with the shipped
default from the start and unrelated to the LanternOps#5265 bug itself. Seeded the
persisted column-visibility preference via `addInitScript` (the Columns
menu that would toggle it in the UI carries no `data-testid`, out of
that wave's file-ownership scope) rather than touch that menu.

## Test evidence

- **New regression test** (`DevicesPage.postCreateHandoff.test.tsx`):
reproduces the exact remount via a stateful fake `AddNetworkAssetModal`
whose internal `created` flag can only survive a `loading` flip if the
real component instance stays mounted. Verified **red** against the
pre-fix `DevicesPage.tsx` (panel disappears), **green** after.
- `apps/web` full suite: **828 files / 9311 tests passed**.
- `npx tsc --noEmit -p .`: clean.
- **E2E** (`e2e-tests/tests/manual-network-asset.spec.ts`) against a
fresh `worktree-stack`: first run confirmed the actual LanternOps#5265 behavior —
hand-off panel appeared and survived the create → refresh flow correctly
— but failed on the unrelated pre-existing `source`-column gap described
above. After the spec fix, re-ran end-to-end: **1 passed**, including
that final assertion.

Closes LanternOps#5265
Refs LanternOps#5228

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01RTMowR8XgvbgZakWhtbiDv

---------

Co-authored-by: Todd Hebebrand <todd@lanternops.io>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>